• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    The present invention relates to implementations including obtaining, through a computer system, a unified blockchain domain name message (a ubcdn) from a blockchain instance, wherein the ubcdn message includes a ubcdn from the blockchain instance, a digital signature of a blockchain instance ubcdn owner (a ubcdn owner) in ubcdn and a ubcdn domain certificate; verifying that the ubcdn domain certificate is issued by a trusted certification authority (ca) using a ca public key; and verifying that ubcdn is issued by the ubcdn owner using a public key from the ubcdn owner. ubcdn's message includes a blockchain domain name and a blockchain instance string identifier uniquely matching the blockchain domain name.
    公开号:BR112019008000A2
    申请号:R112019008000
    申请日:2018-11-16
    公开日:2019-09-10
    发明作者:Qiu Honglin
    申请人:Alibaba Group Holding Ltd；
    IPC主号:
    专利说明:

    "COMPUTER IMPLEMENTED METHOD FOR AUTHENTICATING A DOMAIN NAME, COMPUTER PROGRAM PRODUCT AND SYSTEM FOR IMPLEMENTING A METHOD" Field of the Invention [001] The present invention relates to the methods implemented by computer for a name scheme domain for blockchain systems.
    Background of the Invention [002] Distributed accounting systems (DLSs), which can also be called consensus networks and / or blockchain networks, enable participating entities to store data with security and immutability. DLSs are commonly referred to as blockchain networks without referencing any specific user cases (for example, cryptocurrencies). Examples of types of blockchain networks can include public blockchain networks, private blockchain networks and consortium blockchain networks. A public blockchain network is open for all entities to use DLS and participate in the consensus process. A private blockchain network is provided to a specific entity, which centrally controls read and write permissions. A blockchain consortium network is provided to a select group of entities, which control the consensus process and include an access control layer.
    [003] Blockchains are used in cryptocurrency networks, which enable participants to carry out transactions to buy / sell goods and / or services using a cryptocurrency. A common cryptocurrency includes Bitcoin. In cryptocurrency networks, record keeping models are used to record transactions between users. Examples of record-keeping models include an output model of
    Petition 870190056735, of 6/19/2019, p. 9/62
    2/40 unused transaction (UTXO) and account model (also called account-based model or account / balance model).
    Description of the Invention [004] The realizations of the present invention include the methods implemented by computer for a domain name scheme for blockchain systems. More especially, the achievements of the present invention are aimed at a unified domain name management scheme for cross-chain interactions in blockchain systems.
    [005] In some embodiments, the actions include obtaining, via a computer system, a unified blockchain domain name (UBCDN) message from a blockchain instance, where the UBCDN message includes a UBCDN from the blockchain instance, a digital signature of a UBCDN owner of the blockchain instance (UBCDN owner) in UBCDN and a UBCDN domain certificate; verifying that the UBCDN domain certificate is issued by a trusted certification authority (CA) using a public CA key; and checking whether the UBCDN is issued by the UBCDN owner using a public key from the UBCDN owner. The UBCDN message includes a blockchain domain name and a blockchain instance chain identifier uniquely corresponding to the blockchain domain name. The blockchain instance UBCDN includes a blockchain instance blockchain domain name and a blockchain instance chain identifier uniquely corresponding to the blockchain domain name. The blockchain domain name is a unique identifier of the blockchain instance on a unified blockchain network, including a series of blockchain instances that are communicatively linked by two or more relays. The blockchain domain name includes a readable tag.
    [006] Other achievements include systems, appliances and
    Petition 870190056735, of 6/19/2019, p. 10/62
    3/40 corresponding computer programs, configured to perform the actions of the methods, encoded in computer storage devices.
    [007] These and other achievements may optionally include one or more of the following characteristics:
    - A first feature, which can be combined with any of the following features, in which the computing system acts as a third party in the unified blockchain network;
    - A second feature, combinable with any of the following features, in which the computing system acts as a client node of a second blockchain instance different from the blockchain instance in the unified blockchain network, and the method further includes: in response to the verification that the UBCDN is issued by the owner of UBCDN; and checking whether the UBCDN of UBCDN is issued by a trusted CA, conducting cross-chain transactions between the blockchain instance and the second blockchain instance based on the blockchain domain name of the blockchain instance ·,
    - A third feature, which can be combined with any of the following features, where the UBCDN domain certificate includes: the blockchain domain name of the blockchain instance ·, the public key of the UBCDN owner; and a digital CA signature on the blockchain domain name of the blockchain instance and the public key of the UBCDN owner;
    - A fourth feature, combinable with any of the following resources, in which the CA digital signature is obtained by the CA signature on the blockchain domain name of the blockchain instance and the public key of the UBCDN owner using a CA private key corresponding to the key public CA; and where verification that the UBCDN domain certificate is issued by a trusted CA using a public CA key includes verification that the UBCDN domain certificate is issued by the CA using the domain certificate, the CA digital signature and the public key
    Petition 870190056735, of 6/19/2019, p. 11/62
    4/40 CA;
    - A fifth feature, which can be combined with any of the following features, in which the UBCDN owner’s digital signature is obtained by the UBCDN owner by signing the UBCDN using a private key corresponding to the public key of the UBCDN owner; and where the verification that the UBCDN of the blockchain instance is issued by the UBCDN owner using a public key of the UBCDN owner includes verification that the UBCDN is issued by the UBCDN owner using UBCDN, the digital signature of the UBCDN owner and the public key of the UBCDN owner.
    [008] In some embodiments, actions include obtaining, by a UBCDN owner of a blockchain instance (a UBCDN owner) of a trusted certification authority (CA), of a UBCDN domain certificate of the blockchain instance, where a blockchain instance UBCDN includes: a blockchain instance blockchain domain name and a blockchain instance chain identifier uniquely corresponding to the blockchain domain name, where the chain identifier indicates a blockchain network configuration of blockchain instance ·, where the blockchain domain name is a unique identifier of the blockchain instance on a unified blockchain network including a series of blockchain instances that are communicatively linked by two or more relays, and where the blockchain domain name includes a tag readable, where the UBCDN domain certificate includes: the blockchain domain name of the instance blockchain ·, a public key of the UBCDN owner; and a digital CA signature on the blockchain domain name of the blockchain instance and the public key of the UBCDN owner; the signature, by the UBCDN owner, of the UBCDN of the blockchain instance ·, and the publication, by the UBCDN owner, of a UBCDN message of the blockchain instance, in which the UBCDN message
    Petition 870190056735, of 6/19/2019, p. 12/62
    5/40 includes: the blockchain instance UBCDN ·, a digital signature of the UBCDN owner resulting from the UBCDN signature; and the UBCDN domain certificate.
    [009] Other achievements include the corresponding computer systems, devices and programs, configured to carry out the actions of the methods, encoded in computer storage devices.
    [010] These and other achievements may optionally include one or more of the following characteristics:
    [011] A first feature, combinable with any of the following features, further including: the identification of an updated blockchain chain identifier indicating an updated blockchain network configuration of the blockchain instance, the signature, by the owner of UBCDN, a Updated blockchain instance UBCDN that includes blockchain instance blockchain domain name and updated blockchain instance chain identifier ·, and the publication by the UBCDN owner of an updated blockchain instance UBCDN message, in which the message Updated UBCDN includes: the updated UBCDN of the blockchain instance ·, an updated digital signature of the UBCDN owner resulting from the updated UBCDN signature; and the UBCDN domain certificate.
    [012] The present invention also provides one or more non-transitory, computer-readable storage media coupled to one or more processors and which has instructions stored on them that, when executed by one or more processors, cause one or more processors to perform operations according to the realizations of the methods provided herein.
    [013] The present invention further provides a system for implementing the methods provided herein. The system includes one or
    Petition 870190056735, of 6/19/2019, p. 13/62
    6/40 more processors, and a computer-readable storage medium coupled to one or more processors that have instructions stored on it which, when executed by one or more processors, cause one or more processors to perform operations according to the achievements of the methods provided herein.
    [014] It is considered that the methods according to the present invention can include any combination of the achievements and characteristics described herein. That is, the methods according to the present invention are not limited to the combinations of embodiments and characteristics specifically described herein, but also include any combination of the embodiments and characteristics provided.
    [015] Details of one or more embodiments of the present invention are presented in the accompanying drawings and in the description below. Other features and advantages of the present invention will be apparent from the description and drawings, and from the claims.
    Brief Description of the Drawings [016] Figure 1 illustrates an example of an environment that can be used to carry out the embodiments of the present invention.
    [017] Figure 2 illustrates an example of conceptual architecture according to the realizations of the present invention.
    [018] Figure 3 illustrates an example of the unified blockchain domain name (UBCDN) of a blockchain instance, in accordance with the achievements of the present invention.
    [019] Figure 4 illustrates an example of a UBCDN management scheme in a unified blockchain network, in accordance with the achievements of the present invention.
    [020] Figure 5 illustrates an example of a process for using a blockchain domain name from a blockchain instance for
    Petition 870190056735, of 6/19/2019, p. 14/62
    7/40 cross-chain interactions in a unified blockchain network, in accordance with the achievements of the present invention.
    [021] Figure 6 illustrates an example of a process for authenticating a UBCDN from a blockchain instance, in accordance with the achievements of the present invention.
    [022] Figure 7 describes an example of the process of a UBCDN owner of a blockchain instance (a UBCDN owner), in accordance with the achievements of the present invention.
    [023] Figure 8 illustrates an example of a relay process for cross-chain interactions in a unified blockchain network, in accordance with the achievements of the present invention.
    [024] Similar symbols of reference in the various drawings indicate similar elements.
    Description of Embodiments of the Invention [025] Embodiments of the present invention include computer-implemented methods for a domain name scheme for blockchain systems. More especially, the achievements of the present invention relate to a unified domain name scheme for cross-chain interactions in blockchain systems.
    [026] In some embodiments, the actions include obtaining, via a computer system, a unified blockchain domain name (UBCDN) message from a blockchain instance, where the UBCDN message includes a UBCDN from the blockchain instance, a digital signature of a UBCDN owner of the blockchain instance (UBCDN owner) in UBCDN and a UBCDN domain certificate; verifying that the UBCDN domain certificate is issued by a trusted certification authority (CA) using a public CA key; and checking if the UBCDN is issued by the UBCDN owner using a public key
    Petition 870190056735, of 6/19/2019, p. 15/62
    8/40 of the UBCDN owner. The UBCDN message includes a blockchain domain name and a blockchain instance chain identifier uniquely corresponding to the blockchain domain name. The blockchain instance UBCDN includes a blockchain instance blockchain domain name and a blockchain instance chain identifier uniquely corresponding to the blockchain domain name. The blockchain domain name is a unique identifier of the blockchain instance on a unified blockchain network, including a series of blockchain instances that are communicatively linked by two or more relays. The blockchain domain name includes a readable tag.
    [027] In some embodiments, actions include obtaining, by a UBCDN owner of a blockchain instance (a UBCDN owner) of a trusted certification authority (CA), of a UBCDN domain certificate of the blockchain instance, where a blockchain instance UBCDN includes: a blockchain instance blockchain domain name and a blockchain instance chain identifier uniquely corresponding to the blockchain domain name, where the chain identifier indicates a blockchain network configuration of blockchain instance ·, where the blockchain domain name is a unique identifier of the blockchain instance on a unified blockchain network including a series of blockchain instances that are communicatively linked by two or more relays, and where the blockchain domain name includes a tag readable, where the UBCDN domain certificate includes: the blockchain domain name of the instance blockchain ·, a public key of the UBCDN owner; and a digital CA signature on the blockchain domain name of the blockchain instance and the public key of the UBCDN owner; the signature, by the UBCDN owner, of the UBCDN of the blockchain instance ·, and the publication, by the UBCDN owner, of a UBCDN message of the blockchain instance, in which the UBCDN message
    Petition 870190056735, of 6/19/2019, p. 16/62
    9/40 includes: the UBCDN of the blockchain instance, a digital signature of the UBCDN owner resulting from the UBCDN signature; and the UBCDN domain certificate.
    [028] To provide the additional context for the achievements of the present invention and, as was introduced above, distributed accounting systems (DLSs), which can also be referred to as consensus networks (for example, composed of peer-to- peer), and blockchain networks, enable participating entities to execute transactions securely and immutably and store data. Although the term “blockchain’ ’in general is associated with the Bitcoin cryptocurrency network, blockchain is used at present to, in general, refer to a DLS without reference to any special use case. As presented above, a blockchain network can be provided as a public blockchain network, a private blockchain network or a consortium blockchain network.
    [029] In a public blockchain network, the consensus process is controlled by nodes in the consensus network. For example, hundreds, thousands and even millions of entities can cooperate with a public blockchain network, each operating at least one node on the public blockchain network. Therefore, the public blockchain network can be considered a public network in relation to the participating entities. In some examples, most entities (nodes) must sign each block for the block to be valid and added to the blockchain (distributed accounting) of the blockchain network. An example of a public blockchain network includes the Bitcoin network, which is a peer-to-peer payment network. The Bitcoin network leverages distributed accounting, known as blockchain. As noted above, the term blockchain, however, is used to, in general, refer to distributed accounts without special reference to the Bitcoin network.
    [030] In general, a public blockchain network supports transactions
    Petition 870190056735, of 6/19/2019, p. 17/62
    10/40 public. A public transaction is shared with all nodes within the public blockchain network and is stored on a global blockchain. A global blockchain is a blockchain that is replicated in all nodes. That is, all the nodes are in a perfect state of consensus regarding the global blockchain. To reach consensus (for example, agreeing to add a block to a blockchain), a consensus protocol is implemented on the public blockchain network. An example of a consensus protocol includes, without limitation, proof of work (POW) implemented on the Bitcoin network.
    [031] In general, a private blockchain network is provided to a special entity, which centrally controls read and write permissions. The entity controls which nodes are able to participate in the blockchain network. Consequently, private blockchain networks, in general, are called authorized networks that impose restrictions on who can participate in the network and on their level of participation (for example, only in certain transactions). Various types of access control mechanisms can be used (for example, existing participants vote to add new entities, a regulatory authority can control admission).
    [032] In general, a consortium blockchain network is private between participating entities. In a blockchain consortium network, the consensus process is controlled by an authorized set of nodes, one or more nodes being operated by a respective entity (for example, a financial institution, insurance company). For example, a consortium of ten (10) entities (for example, financial institutions, insurance companies) can operate a consortium blockchain network, each operating at least one node in the consortium blockchain network. Consequently, the consortium blockchain network can be considered a private network in relation to the participating entities. In some examples, each entity (node) must
    Petition 870190056735, of 6/19/2019, p. 18/62
    11/40 sign all blocks so that the block is valid and added to the blockchain. In some examples, at least a subset of entities (nodes) (for example, at least 7 entities) must sign each block for the block to be valid and added to the blockchain.
    [033] The achievements of the present invention are described in greater detail herein with reference to a blockchain consortium network. It is contemplated, however, that the achievements of the present invention can be carried out on any suitable type of blockchain network.
    [034] The realizations of the present invention are described in greater detail in the present, in view of the above context. More particularly, and as introduced above, the achievements of the present invention are intended for a domain name scheme for cross-chain interactions in blockchain systems.
    [035] Various blockchain platforms, environments or products have been developed based on different blockchain technologies. Examples of blockchain products include Ethereum and Bitcoin. The current blockchain network includes several blockchain instances deployed based on the different blockchain products. For example, the current blockchain network includes several blockchain instances, such as public blockchains, private blockchains or consortium blockchains developed based on Ethereum or Bitcoin technologies.
    [036] The current access mode of each blockchain instance requires access from a client node (also referred to as a client terminal) of the blockchain or its technical components, such as the SDKs. To accurately connect to a specific blockchain instance, the customer needs to load their blockchain network settings. These blockchain network configurations are typically hashed, member certificates, and the like. These configurations are unreadable for humans and it is difficult to identify which chains the
    Petition 870190056735, of 6/19/2019, p. 19/62
    12/40 configurations identify.
    [037] The present invention provides a domain name scheme for the blockchain network. Specifically, a unified blockchain domain name (UBCDN) is provided to act as a unique identifier for each blockchain instance (also referred to as a blockchain network instance or a chain) on the blockchain network. A blockchain instance, for example, can be an implementation or deployment of a blockchain based on a blockchain platform or technology (for example, Ethereum). Each UBCDN unites a blockchain instance domain name (also called a blockchain domain name) with a corresponding blockchain network configuration (also called a blockchain network configuration). In some embodiments, the blockchain network configuration can be represented or indicated by a chain identifier. A client node of a blockchain instance can obtain a corresponding blockchain network configuration by analyzing the UBCDN to identify the chain identifier. Based on the blockchain network configuration, the client node can link to or otherwise access the specific blockchain instance.
    [038] The domain name scheme described can provide a unified protocol for interactions between blockchain systems on a unified (or global) blockchain network that includes multiple or all deployed blockchain instances, based on different blockchain products or technologies. All blockchain instances on the unified blockchain network follow the same domain name scheme and receive exclusive UBCDNs. In some embodiments, each blockchain instance on the unified blockchain network is assigned to a single UBCDN that can be recognized by all blockchain instances on the unified blockchain network, regardless of different platforms, technologies or relays used on the unified blockchain network. In
    Petition 870190056735, of 6/19/2019, p. 20/62
    13/40 some achievements, the UBCDN defines a domain of administrative autonomy, authority or control of a blockchain instance within the unified blockchain network. In some embodiments, the unified blockchain network can be considered as a counterpart of the Internet to the IP network, while UBCDN can be considered as a mapping of a domain name of an IP resource on the IP network with an IP address of the IP resource.
    [039] Each blockchain instance in the unified blockchain network can be uniquely identified by a corresponding UBCDN, in order to facilitate multiple or cross-chain communications. For example, unlike existing cross-chain achievements like COSMOS, which uses a relay chain for cross-chain interactions, in which each blockchain is assigned an identifier (ID) within the relay chain network, but the ID has a local scope and cannot be reused in other relay chain networks, in the domain name scheme described, the UBCDN can be used and is globally recognizable by all blockchain instances in the unified blockchain network, despite how many relay chains are included in the unified blockchain network.
    [040] In addition, the domain name scheme described simplifies the identification or addressing protocol for cross-chain interactions in blockchain systems. For example, in the domain name scheme described, a single UBCDN is sufficient to uniquely identify a blockchain instance and is globally recognizable by all blockchain instances in the unified blockchain network for interactions between different blockchain networks, while in COSMOS , a blockchain instance is assigned to several different IDs when the blockchain instance associates with multiple relay chains for the blockchain instance to interact with other blockchains.
    [041] In addition, the UBCDN may include an identifier or
    Petition 870190056735, of 6/19/2019, p. 21/62
    14/40 readable label, helping users to memorize and easily reach a blockchain instance, therefore promoting the adoption or use of the blockchain instance. As an example, owners or operators of public blockchains, private blockchains or consortium blockchains can select blockchain domain names that match their names, helping users remember blockchain instance identifiers and making translation, resolution or identification even easier. other chain identifiers corresponding to blockchain domain names, accelerating cross-chain interactions on the unified blockchain network.
    [042] In addition to providing easily recognizable and memorable names for identifying blockchain instances, the UBCDN allows a blockchain instance to retain its blockchain domain name even if the underlying network configuration of the blockchain instance is changed (for example, through system update or move or migration to a different physical location in the network address topology). In the event of such a change or update, the chain identifier of the blockchain instance can be changed while the name of the blockchain domain can remain the same. The UBCDN owner can change the mapping of the blockchain domain name to the updated chain identifier and allow others (e.g., other blockchain instances or client nodes) to use the same blockchain domain name to address and access the blockchain instance.
    [043] Figure 1 illustrates an example of an environment (100) that can be used to carry out the embodiments of the present invention. In some examples, the sample environment (100) allows entities to participate in a blockchain consortium network (102). The example environment (100) includes computing devices or systems (106), (108) and a network (110). In some examples, the network (110) includes a local area network (LAN),
    Petition 870190056735, of 6/19/2019, p. 22/62
    15/40 distance (WAN), Internet or one of its combinations, and connects to websites, user devices (for example, computing devices) and back-end systems. In some examples, the network (110) can be accessed via a wired and / or wireless communication link.
    [044] In the example described, the computing systems (106), (108) can include each suitable computing system that makes it possible to participate as a node in the consortium blockchain network (102). Examples of computing devices include, without limitation, a server, a desktop computer, a laptop computer, a tablet computing device and a smartphone. In some examples, the computing systems (106), (108) host one or more services implemented per computer to interact with the consortium blockchain network (102). For example, the computing system (106) can host the services implemented by a first entity's computer (for example, user A), as a transaction management system that the first entity uses to manage its transactions with one or more entities (for example, other users). The computing system (108) can host the computer-implemented services of a second entity (for example, user B), as a transaction management system that the second entity uses to manage its transactions with one or more other entities ( for example, other users). In the example in Figure 1, the consortium blockchain network (102) is represented as a network of peer-to-peer nodes, and the computing systems (106), (108) provide the nodes of the first entity and second entity, respectively , participating in the consortium blockchain network (102).
    [045] Figure 2 illustrates an example of conceptual architecture (200) according to the embodiments of the present invention. The example conceptual architecture (200) includes an entity layer (202), a services layer
    Petition 870190056735, of 6/19/2019, p. 23/62
    16/40 hosted (204) and a blockchain network layer (206). In the illustrated example, the entity layer (202) includes three entities, Entity_1 (E1), Entity_2 (E2) and Entity_3 (E3), each entity has a respective transaction management system (208).
    [046] In the example described, the hosted services layer (204) includes the interfaces (210) for each transaction management system (208). In some examples, a transaction management system (208) communicates with a respective interface (210) on a network (for example, the network (110) in Figure 1) using a protocol (for example, the data transfer protocol) secure hypertext (HTTPS)). In some examples, each interface (210) provides a communication connection between a transaction management system (208) and the blockchain network layer (206). More especially, the interface (210) communicates with a blockchain network (212) of the blockchain network layer (206). In some examples, communication between an interface (210) and the blockchain network layer (206) is conducted using remote procedure links (RPCs). In some examples, interfaces (210) "host" blockchain network nodes for the respective transaction management systems (208). For example, interfaces (210) provide the application programming interface (API) for accessing the blockchain network (212).
    [047] As described in the present, the blockchain network (212) is provided as a peer-to-peer network including a number of nodes (214) that record the immutable information on a blockchain (216). Although a single blockchain (216) is schematically illustrated, several copies of the blockchain (216) are provided and maintained through the blockchain network (212). For example, each node (214) stores a copy of the blockchain. In some embodiments, the blockchain (216) stores information associated with transactions that are carried out between two or more participating entities
    Petition 870190056735, of 6/19/2019, p. 24/62
    17/40 of the consortium blockchain network.
    [048] Figure 3 illustrates an example of a unified blockchain domain name (UBCDN) (300) of a blockchain instance, in accordance with the achievements of the present invention. The UBCDN (300) can include a blockchain domain name (310) and a corresponding chain identifier (320) of the blockchain instance. The blockchain domain name (310) can be readable by human reading. The chain identifier (320) can indicate a blockchain network configuration of the blockchain instance and allows access to the blockchain instance based on the blockchain network settings. In some embodiments, the UBCDN (300) may include additional fields or be illustrated as a string or other data structure.
    [049] The blockchain domain name (310) can be easy to use. For example, the blockchain domain name (310) can be a text-based tag that is easier to remember than the corresponding numeric string identifier (320) (for example, a 40-character hexadecimal address used in the Ethereum protocols In some embodiments, the blockchain domain name is (310) can be illustrated as a wire or other data structure.
    [050] In some embodiments, the blockchain domain name (310) may have a defined syntax to further facilitate the understanding of the source, property or organization of the underlying blockchain instance. For example, the blockchain domain name (310) can be designed similarly to the domain name on the IP network. The blockchain domain name (310) can include one or more parts or tags. One or more tags can be concatenated and have a hierarchy of domains descending from the tag from right to left in the name. Each tag on the left specifies a subdivision or subdomain of the domain on the right. For example, a blockchain domain name (310) of the chain. Organization indicates that the chain
    Petition 870190056735, of 6/19/2019, p. 25/62
    18/40 chain blockchain instance is a subdomain of the organization domain and belongs to the organization. In some embodiments, the blockchain domain name (310) may define an additional or different syntax.
    [051] The chain identifier (320) can include an addressable identifier that is used to address and access the blockchain instance on the blockchain network. The chain identifier (320) can indicate a blockchain network configuration of the blockchain instance and allows access to the blockchain instance based on the blockchain network settings. For example, several blockchain instances can be deployed based on Ethereum's technology. The blockchain instance, for example, can be a mainnet chain, a test chain, a private chain or a consortium chain. An Ethereum customer can establish a connection to an Ethereum blockchain instance by loading the genesis block (i.e., the first block) of the Ethereum blockchain instance. The genesis block is equivalent to a unique identifier for the Ethereum blockchain instance. Consequently, in some embodiments, one or more fields (e.g., a hash value) from the genesis block of an Ethereum blockchain instance can be extracted as the chain identifier (320) of the Ethereum blockchain instance. In some embodiments, the chain identifier of a blockchain instance may include a hash value from a blockchain genesis block as well as a network ID that identifies the blockchain instance. In some embodiments, the network ID makes it possible for transactions on the blockchain instance to look different from those of other chains, for example, by signing transactions differently, depending on the network ID used. As such, the network ID indicates an additional network configuration that can be used to link or access the blockchain instance. The chain identifier (320) can include additional or different components or fields, for example, depending on the underlying blockchain technology or platform of the instance
    Petition 870190056735, of 6/19/2019, p. 26/62
    19/40 blockchain.
    [052] The UBCDN (300) creates a one-to-one mapping of the blockchain domain name (310) and its corresponding chain identifier (320) of the blockchain instance. By providing the blockchain domain name (310), its corresponding chain identifier (320) can be translated, resolved or otherwise identified, and vice versa. As such, a node can access the blockchain instance based on the blockchain network configuration indicated by the chain identifier (320). As an analogy, the blockchain domain name (310) of a blockchain instance is similar to a domain name according to the Domain Name System (DNS) of an Internet Protocol (IP) resource (for example, example .com) and the string identifier (320) is similar to the IP address of the IP resource on the IP network.
    [053] In some embodiments, for a given blockchain domain name (310), its corresponding string identifier (320) can be translated, resolved or otherwise identified using the UBCDN query information that is cached or stored locally , inside a query computer or remotely on the unified blockchain network (for example, on a central UBCDN server). The UBCDN query information can include several UBCDN (300), each UBCDN (300) corresponding to several blockchain instances. UBCDN query information can be stored, for example, in a lookup table or in another data structure. One or more nodes (for example, a client node, a consensus node or a relay node) or a server on the unified blockchain network can store UBCDN query information. When searching based on UBCDN query information, a chain identifier (320) corresponding to a given blockchain domain name (310) can be identified and vice versa.
    Petition 870190056735, of 6/19/2019, p. 27/62
    20/40 [054] When UBCDN information is cached locally, the UBCDN query process can be faster than performing a remote UBCDN query, for example, on a remote UBCDN server. In some realizations, in the last remote UBCDN query, a user enters a blockchain domain name (310), for example, “chainl. organization in an SDK of the user’s computing device (ie, the client node). The client node sends a request or query that includes the blockchain domain name (310) “chainl. organization to a remote UBCDN server, for example, via the Internet outside the chain. Upon receiving the request, the remote UBCDN server searches the UBCDN query information for an entry corresponding to the blockchain domain name (310) “chainl. organization ’and identifies the chain identifier (320) corresponding to the blockchain domain name (310). Then, the remote UBCDN server responds to the client node with the chain identifier (320) corresponding to the blockchain domain name (310), for example, sending a response including the chain identifier (320) corresponding to the blockchain domain name ( 310) for the customer node.
    [055] Figure 4 illustrates an example of a UBCDN (400) management scheme in a unified blockchain network, in accordance with the achievements of the present invention. The example of the UBCDN (400) management scheme can provide enhanced confidence and security for UBCDN-based cross-chain communications. In some embodiments, the UBCDN (400) example management scheme relies on a public key infrastructure (PKI) to establish trust in the unified blockchain network.
    [056] For example, a certification authority (CA) (410) (for example, the PKI operator) can be used. CA (410) issues a domain certificate (“Domain Cert”) (420a), (420b) and (420c) (collectively, domain certificate (420)) for each owner of a UBCDN (430a), (430b) and (430c)
    Petition 870190056735, of 6/19/2019, p. 28/62
    21/40 (collectively, owner of UBCDN (430)). The owner of UBCDN (430), for example, may be an owner or operator of the blockchain instance. As illustrated, the UBCDN owner (430a) owns a blockchain domain name “Examplel .chain”, the UBCDN owner (430b) owns a blockchain domain name “Example2.chain” and the owner of UBCDN ( 430b) owns a blockchain domain name “ExampleN. chain. ” [057] In some embodiments, the UBCDN owner (430) can obtain a domain certificate (420) by applying to the CA (410) a certificate signing request (not shown in Figure 4). In some embodiments, the certificate request is an electronic document that contains the blockchain domain name, blockchain instance information (for example, the chain identifier or other network configurations) and a public key of the UBCDN owner (430). After verifying that the UBCDN the owner (430) has the right to administratively manage the blockchain domain name of the blockchain instance, the CA (410) can sign the request, thereby producing a public domain certificate (420). In some embodiments, the domain certificate (420) can be served to any node (for example, a customer node, a consensus node or a relay node) that would like to access the underlying blockchain instance of the blockchain domain name (for example example, “Examplel .chain”) and proof for the node that CA (410) trusts and issued a certificate to the UBCDN owner (430).
    [058] The domain certificate (420) can include a blockchain domain name (for example, “Examplel .chain”) and a public key of the UBCDN owner (430). The UBCDN owner (430) is the holder of the private key corresponding to the public key. CA (410) can digitally sign the blockchain domain name and the owner's public key
    Petition 870190056735, of 6/19/2019, p. 29/62
    22/40 of UBCDN (430) using the CA's own private key. The domain certificate (420) can include the digital signature signed by the CA (410) on the blockchain domain name and the public key of the UBCDN owner (430).
    [059] As described in relation to Figure 3, a UBCDN can include a blockchain domain name (for example, “Examplel .chain”) and a corresponding chain identifier. The UBCDN owner (430) can publish the UBCDN and sign the UBCDN using the private key of the UBCDN owner (430). In some embodiments, the UBCDN owner (430) publishes one or more UBCDN messages (for example, the UBCDN messages (440a), (450a), (440)) so that the UBCDN can be authenticated or verified.
    [060] In some embodiments, UBCDN messages (440) may include UBCDN, a resulting UBCDN digital signature, and a domain certificate. The domain certificate can be the respective domain certificate (420) received from the CA (410). The UBCDN can include the blockchain domain name and the chain identifier (for example, the blockchain domain name (310) and the chain identifier (320), as described in relation to the Figure). As illustrated, the UBCDN owner (430a) issues a UBCDN message (440a) that includes the blockchain domain name (442a) “Examplel .chain” and a corresponding chain identifier (444a) “Chain Identifier V0”, a signature digital (446a) and a domain certificate (448a). The domain certificate (448a) can be the domain certificate (420a) issued by the CA (410) and received by the UBCDN owner (430a) from the CA (410). The digital signature (446a) can result from the signature of the UBCDN owner (430a) of UBCDN (ie the blockchain domain name (442a) “Examplel .chain” and a corresponding chain identifier (444a) “Chain Identifier V0” in this case) using the private key of the UBCDN owner (430a).
    Petition 870190056735, of 6/19/2019, p. 30/62
    23/40 [061] Similarly, the UBCDN owner (430b) issues a UBCDN message (440b) that includes the blockchain domain name (442b) “Example2.chain” and a corresponding string identifier (444b) “ Chain Identifier Vx ”, a digital signature (446b) and a domain certificate (448b). The domain certificate (448b) can be the domain certificate (420b) issued by the CA (410) and received by the UBCDN owner (430b) from the CA (410). The digital signature (446a) can result from the UBCDN signature by the UBCDN owner (430b) (ie, the blockchain domain name (442b) “Example2.chain” and a corresponding chain identifier (444a) “Chain Identifier V0” in this case) using the private key of the UBCDN owner (430b).
    [062] In some embodiments, an authentication or verification process can be performed, for example, by any node in the unified blockchain network or a third party to verify the validity of a UBCDN based on the UBCDN message. This can ensure the security that is important for e-commerce, especially in connection with mobile payment transactions for cross-chain interactions in blockchain systems.
    [063] In some embodiments, the authentication or verification process may include, for example, verifying that the blockchain domain name is the same as the blockchain domain name in the domain certificate; verification that the UBCDN owner (for example, the UBCDN owner (430a)) is the holder of the blockchain domain name (for example, “the blockchain domain name (442a)” Examplel .chain “) by verifying the digital signature in UBCDN (for example, the digital signature (446a)) using the public key in the domain certificate (for example, the domain certificate (420a)) issued by the CA (410) and checking whether the domain certificate (for example , the domain certificate (448a)) is issued by the trusted CA (410).
    Petition 870190056735, of 6/19/2019, p. 31/62
    24/40 [064] In some embodiments, after checking the validity of UBCDN, for example, based on the authentication or verification process, a client node can use UBCDN for cross-chain interactions on the unified blockchain network. For example, the client node can receive and read a UBCDN message, check the validity or legality of UBCDN and confirm that the UBCDN is issued by the UBCDN owner; and then use the UBCDN to uniquely identify and access the blockchain instance, for example, by identifying the string identifier corresponding to the blockchain domain name in UBCDN.
    [065] Figure 5 illustrates an example process (500) for using a blockchain domain name from a blockchain instance for cross-chain interactions in a unified blockchain network, in accordance with the achievements of the present invention. In some embodiments, the example process (500) can be performed using one or more computer executable programs executed using one or more computing devices. For clarity of presentation, the following description generally describes the process (500) in the context of the other figures in this description. For example, the example process (500) can be performed by a client node of a first blockchain instance, such as the computing system (106) or (108) of the consortium blockchain network (102) as described in relation to Figure 1, or the node (214) of the blockchain network (212), as described in relation to Figure 2. However, it will be understood that the process (500) can be performed, for example, through any system, environment, software and hardware, or a combination of systems, environments, software and hardware, as appropriate. In some embodiments, several process steps (500) can be performed in parallel, in combination, in links or in any order.
    [066] In (510), a customer node of a first instance
    Petition 870190056735, of 6/19/2019, p. 32/62
    25/40 blockchain obtains a blockchain domain name from a different second blockchain instance. In some embodiments, the first blockchain instance and the second blockchain instance are broken down based on different blockchain platforms. In some embodiments, the first blockchain instance and the second blockchain instance belong to different owners or operators. The first blockchain instance and the second blockchain instance are on a unified blockchain network, including several blockchain instances that are communicatively linked by two or more relays.
    [067] The blockchain domain name is a unique identifier for the second blockchain instance in the unified blockchain network, even if the unified blockchain network includes two or more relays. In some embodiments, each of the blockchain instance numbers on the unified blockchain network has only one blockchain domain name that uniquely identifies each of the blockchain instance numbers on the unified blockchain network.
    [068] The blockchain domain name includes a readable tag. In some embodiments, the readable label includes a text-based label. The blockchain domain name uniquely corresponds to a chain identifier of the second blockchain instance. The blockchain domain name and chain identifier can be illustrated by a UBCDN such as UBCDN (300), as described in Figure 3. As an example, the blockchain domain name can be the blockchain domain name (310), while the string identifier can be the corresponding string identifier (320) in UBCDN (300).
    [069] At (520), the client node of the first blockchain instance identifies the chain identifier of the second blockchain instance based on the blockchain domain name of the second blockchain instance, where the chain identifier of the second blockchain instance indicates a configuration of blockchain network of the second blockchain instance. In some achievements, the
    Petition 870190056735, of 6/19/2019, p. 33/62
    26/40 chain identifier of the second blockchain instance includes a hash value of a genesis block of the second blockchain instance and a network identifier of the second blockchain instance, for example, as described in relation to Figure 3.
    [070] In some embodiments, identifying the chain identifier of the second blockchain instance based on the blockchain domain name includes identifying the chain identifier of the second blockchain instance according to the query information stored locally in the client node based on the name blockchain domain name.
    [071] In some embodiments, identifying the chain block identifier of the second blockchain instance based on the blockchain domain name includes identifying the chain identifier of the second blockchain instance of a remote unified blockchain domain name server based on the blockchain domain name . For example, the client node of the first blockchain instance sends a request or query to the blockchain's unified domain name server. The request includes the blockchain domain name to identify the chain identifier of the second blockchain instance. Then, the client node of the first blockchain instance receives, from the unified blockchain domain name server, a response to the request, where the response includes the chain identifier of the second blockchain instance.
    [072] At (530), the client node of the first blockchain instance accesses the second blockchain instance based on the blockchain network configuration indicated by the chain identifier of the second blockchain instance. For example, the first blockchain instance accesses the second blockchain instance through a client node of the second blockchain instance based on the hash value of the genesis block of the second blockchain instance indicated by the chain identifier of the second instance
    Petition 870190056735, of 6/19/2019, p. 34/62
    27/40 blockchain. In some embodiments, the first blockchain instance accesses the second blockchain instance through a client node of the second blockchain using a relay (for example, a relay node or a relay chain) or another application that is communicatively linked to the first blockchain instance and the second blockchain instance.
    [073] In some embodiments, to access and retrieve data from the second blockchain instance, the client node of the second blockchain instance can configure a network configuration, such as an IP address and port number for a node (for example, a node consensus) of the second blockchain, and the hash value of the genesis block of the second blockchain instance. The client node of the second blockchain instance can connect to the node of the second blockchain instance through the IP address and port number of the node of the second blockchain instance. The client node of the second blockchain instance can read, retrieve, download or retrieve the node data from the second blockchain instance and verify that the data obtained comes from the second blockchain instance, for example, based on a Simple Payment Verification protocol (SPV) of the second blockchain instance to determine whether the data obtained points to the hash value of the genesis block of the second blockchain instance.
    [074] At (540), the client node of the first blockchain instance performs cross-transactions between the first blockchain instance and the second blockchain instance based on the blockchain domain name of the second blockchain instance. In some embodiments, cross-transaction between the first blockchain instance and the second blockchain instance includes the submission, by the first blockchain instance, of a cross request that includes the blockchain domain name of the second blockchain instance and a data request, for a relay that is communicatively linked to the first blockchain instance and the second blockchain instance. The relay receives the
    Petition 870190056735, of 6/19/2019, p. 35/62
    28/40 cross-chain request and reads the blockchain domain name from the second blockchain instance, loads the corresponding blockchain network configuration from the second blockchain instance, uses the configuration to connect to the second blockchain instance. The relay can retrieve, download or receive the requested data from the second blockchain instance and send the requested data to the first blockchain instance.
    [075] Figure 6 illustrates an example process (600) for authenticating a UBCDN from a blockchain instance, in accordance with the achievements of the present invention. In some embodiments, the example process (600) can be performed using one or more computer executable programs executed using one or more computing devices. For clarity of presentation, the following description generally describes the process (600) in the context of the other figures in this description. For example, the example process (600) that can be performed by the computing system (106) or (108) of the consortium blockchain network (102), as described in relation to Figure 1, or the node (214) of the network blockchain (212), as described in relation to Figure 2. However, it will be understood that the process (600) can be carried out, for example, through any suitable system, environment, software and hardware, or a combination of systems, environments , software and hardware, as appropriate. In some embodiments, several process steps (600) can be performed in parallel, in combination, in links or in any order.
    [076] At (610), a computing system obtains a unified blockchain domain name (UBCDN) message from a blockchain instance. In some embodiments, the computing system is a third of the unified blockchain network. In some embodiments, the computing system is a client node of a second blockchain instance different from the blockchain instance on the unified blockchain network.
    Petition 870190056735, of 6/19/2019, p. 36/62
    29/40 [077] The UBCDN message, for example, can be the UBCDN message (440), as described in relation to Figure 4. The UBCDN message includes a UBCDN from the blockchain instance, a digital signature from an owner of UBCDN to UBCDN; and a UBCDN domain certificate.
    [078] The blockchain instance UBCDN includes a blockchain domain name of the blockchain instance, where the blockchain domain name is a unique identifier of the blockchain instance on a unified blockchain network including a number of blockchain instances that are communicatively linked by two or more relays. The blockchain domain name includes a readable tag and a chain identifier for the blockchain instance uniquely corresponding to the blockchain domain name.
    [079] In some embodiments, the UBCDN domain certificate includes the blockchain domain name of the blockchain instance, the public key of the UBCDN owner and a digital CA signature on the blockchain domain name of the blockchain instance and the key public of the owner of UBCDN.
    [080] At (620), the computing system verifies that the UBCDN domain certificate is issued by a trusted certification authority (CA) using a public CA key. In some embodiments, the CA digital signature is obtained by the CA signature on the blockchain domain name of the blockchain instance and the public key of the UBCDN owner using a CA private key corresponding to the CA public key. In some embodiments, verification that the UBCDN domain certificate is issued by a trusted CA using a public CA key includes verification that the UBCDN domain certificate is issued by the CA using the domain certificate, the CA digital signature. and the CA public key.
    [081] No (630), in response to the verification that the certificate of
    Petition 870190056735, of 6/19/2019, p. 37/62
    30/40 UBCDN domain is issued by the CA, the computing system checks whether the UBCDN is issued by the UBCDN owner using a public key from the UBCDN owner. In some embodiments, the UBCDN owner 's digital signature is obtained by the UBCDN owner by signing the UBCDN using a private key corresponding to the public key of the UBCDN owner. In some embodiments, verifying that the UBCDN of the blockchain instance is issued by the UBCDN owner using a public key of the UBCDN owner includes verification that the UBCDN is issued by the UBCDN owner using UBCDN, the UBCDN digital signature of the owner of UBCDN and the public key of the UBCDN owner. For example, the UBCDN owner can sign the UBCDN using the owner's private key and generate a digital signature, for example, according to a signature algorithm. The computing system as the recipient of the UBCDN message can determine whether the UBCDN is issued by the UBCDN owner using the UBCDN, the digital signature and the owner's public key, for example, according to a signature verification algorithm.
    [082] At (640), in response to checking whether the UBCDN is issued by the UBCDN owner, the computing system performs cross-transactions between the blockchain instance and the second blockchain instance based on the blockchain domain name of the blockchain instance, for example, according to the example process (500), as described in relation to Figure 5.
    [083] Figure 7 illustrates a process example (700) of a UBCDN owner of a blockchain instance (a UBCDN owner), in accordance with the achievements of the present invention. In some embodiments, the sample process (700) can be performed using one or more computer executable programs executed using one or more
    Petition 870190056735, of 6/19/2019, p. 38/62
    31/40 computing devices. For clarity of presentation, the following description generally describes the process (700) in the context of the other figures in this description. For example, the sample process (700) can be performed by the UBCDN owner (430) as described in relation to Figure 4. However, it will be understood that the process (700) can be performed, for example, through any system , environment, software and hardware, or a combination of systems, environments, software and hardware, as appropriate. In some embodiments, several process steps (700) can be performed in parallel, in combination, in links or in any order.
    [084] At (710), a UBCDN owner of a blockchain instance (a UBCDN owner, like the UBCDN owner (430)) obtains from a trusted certification authority (CA) (e.g. CA ( 410)), a domain certificate (for example, the UBCDN domain certificate (420) of the blockchain instance. The blockchain instance UBCDN includes a blockchain instance blockchain domain name and a blockchain instance chain identifier uniquely corresponding to the blockchain domain name. The UBCDN, for example, can be the UBCDN (300), as described in relation to Figure 3. The blockchain domain name is a unique identifier of the blockchain instance on a unified blockchain network, including a number of blockchain instances that are communicatively linked by two or more relays. In some embodiments, the blockchain domain name includes a readable tag. The chain identifier indicates a blockchain network configuration of the blockchain instance.
    [085] The UBCDN domain certificate includes the blockchain domain name of the blockchain instance, a public key of the UBCDN owner and a digital CA signature on the blockchain domain name of the blockchain instance and the public key of the UBCDN owner. The UBCDN domain certificate, for example, can be the domain certificate (420),
    Petition 870190056735, of 6/19/2019, p. 39/62
    32/40 as described in relation to Figure 4 [086] No (720), the UBCDN owner signs the UBCDN of the blockchain instance, for example, using the private key of the UBCDN owner, for example, according to an algorithm of signature.
    [087] At (730), the UBCDN owner publishes a UBCDN message (for example, the UBCDN message (440a) or (440b)) from the blockchain instance. The UBCDN message includes the UBCDN of the blockchain instance, a digital signature of the UBCDN owner resulting from the UBCDN signature, and the UBCDN domain certificate.
    [088] At (740), the UBCDN owner identifies an updated blockchain instance chain identifier indicating an updated blockchain network configuration of the blockchain instance. For example, a modification or update of the blockchain network configuration of the blockchain instance may occur (for example, due to the system update or the movement of the physical location of one or more computing devices, such as the genesis block). The chain identifier can be updated to reflect the update of the blockchain network blockchain configuration of the blockchain instance (for example, by updating the hash value of the blockchain instance genesis block). For example, as illustrated in Figure 4, for the same blockchain domain name (442a) “Examplei .chain”, the chain identifier (444a) “Chain Identifier V0” has been updated to a chain identifier (454a) “Chain Identifier V1 ”, to reflect the modification of the blockchain network configuration of the blockchain instance.
    [089] At (750), the UBCDN owner signs an updated UBCDN from the blockchain instance, for example, using the UBCDN owner's private key. The updated UBCDN of the blockchain instance includes the blockchain domain name of the blockchain instance and the updated chain identifier of the blockchain instance. For example, as illustrated in Figure 4,
    Petition 870190056735, of 6/19/2019, p. 40/62
    33/40 the updated blockchain instance UBCDN includes the same blockchain domain name (442a) “Examplel .chain” and the updated chain identifier (454a) “Chain Identifier V1”.
    [090] At (760), the UBCDN owner publishes an updated UBCDN message from the blockchain instance. The updated UBCDN message includes the updated UBCDN from the blockchain instance, an updated digital signature from the UBCDN owner resulting from the updated UBCDN signature, and the UBCDN domain certificate. For example, as illustrated in Figure 4, the UBCDN owner (430a) issues an updated UBCDN message (450) which includes the blockchain domain name (442a) “Examplei .chain” and the updated chain identifier (454a) “ Chain identifier V1 ”, a digital signature (456a) and a domain certificate (458a). The domain certificate (458a) can be the domain certificate (420a) issued by the CA (410) and received by the owner of UBCDN (430a) from the CA (410). The updated digital signature (456a) may result from the signature by the UBCDN owner (430a) of the updated UBCDN (ie the blockchain domain name (442a) “Examplel .chain” and the updated chain identifier (454a) “Chain Identifier V0 ”in this case) using the private key of the UBCDN owner (430a).
    [091] Figure 8 illustrates a process example (800) of a relay for cross-chain interactions in a unified blockchain network, in accordance with the achievements of the present invention. The unified blockchain network includes several blockchain instances that are communicatively linked by two or more relays. In some embodiments, the example process (800) can be performed using one or more computer executable programs executed using one or more computing devices. For clarity of presentation, the following description generally describes the process (800) in the context of the other figures in this description. For example, the example of
    Petition 870190056735, of 6/19/2019, p. 41/62
    34/40 process (800) that can be performed by the relay on a unified blockchain network. However, it will be understood that the process (800) can be carried out, for example, through any suitable system, environment, software and hardware, or a combination of systems, environments, software and hardware, as appropriate. For example, the relay can be a node (for example, the computing system (106) or (108) as described in relation to Figure 1 or the node (214) as described in relation to Figure 2), a blockchain instance ( for example, a blockchain network (102) or the blockchain network (212)), or another computer system on the unified blockchain network. In some embodiments, several process steps (800) can be performed in parallel, in combination, in links or in any order.
    [092] At (810), the relay that is communicatively linked with a first blockchain instance and a second blockchain instance on the unified blockchain network identifies a blockchain domain name from a first blockchain instance. The blockchain domain name of the first blockchain instance is a unique identifier of the first blockchain instance and uniquely corresponds to a chain identifier of the first blockchain instance in the unified blockchain network. In some embodiments, the blockchain domain name of the first blockchain instance includes a first readable tag.
    [093] At (820), the relay identifies a blockchain domain name from the second blockchain instance. The blockchain domain name of the second blockchain instance is a unique identifier of the second blockchain instance and uniquely corresponds to a chain identifier of the second blockchain instance on the unified blockchain network. In some embodiments, the blockchain domain name of the second blockchain instance includes a second readable tag.
    [094] In some embodiments, a relay may designate a
    Petition 870190056735, of 6/19/2019, p. 42/62
    35/40 local identifier for each blockchain that is communicatively linked. The local identifier is designated for the use of the relay and cannot be used by other nodes or relays on the unified blockchain network. In some embodiments, identifying a blockchain domain name of the first blockchain instance includes using the blockchain domain name of the first blockchain instance as the local identifier of the first blockchain instance or replacing the local identifier of the first blockchain instance with the domain name blockchain the first blockchain instance. Similarly, the identification of a blockchain domain name of the second blockchain instance includes using the blockchain domain name of the second blockchain instance as the local identifier of the second blockchain instance or replacing the unique identifier of the second blockchain instance with the domain name blockchain of the second blockchain instance.
    [095] At (830), the relay receives an access request to access the second blockchain instance. The access request includes the blockchain domain name of the second blockchain instance.
    [096] At (840), the relay identifies the chain identifier of the second blockchain instance based on the blockchain domain name of the second blockchain instance. The chain identifier of the second blockchain instance indicates a blockchain network configuration of the second blockchain instance.
    [097] In some embodiments, identifying the second blockchain instance chain identifier based on the second blockchain instance blockchain domain name includes identifying the second blockchain instance chain identifier, according to the query information stored locally on the relay. the blockchain domain name.
    [098] In some embodiments, identifying the chain identifier of the second blockchain instance based on the blockchain domain name of
    Petition 870190056735, of 6/19/2019, p. 43/62
    36/40 second blockchain instance includes identifying the chain identifier of the second blockchain instance based on the blockchain domain name of the second blockchain instance of a remote unified blockchain domain name server.
    [099] At (850), the relay provides access to the second blockchain instance for the first blockchain instance based on the blockchain network configuration indicated by the chain identifier of the second blockchain instance. In some embodiments, the relay provides access to the second blockchain instance for the first blockchain instance, according to a communication protocol designed for cross-chain interactions. For example, the relay can load the blockchain network configuration indicated by the chain identifier of the second blockchain instance corresponding to the blockchain domain name of the second blockchain instance. The relay uses the blockchain network configuration to connect to the second blockchain instance, obtains a result requested by the first blockchain instance of the second blockchain instance, and returns the result requested by the first blockchain instance to the first blockchain instance, according to the techniques of example described in relation to Figure 5.
    [0100] In some embodiments, providing, by the relay, access to the second blockchain instance for the first blockchain instance based on the blockchain network configuration indicated by the chain identifier of the second blockchain instance includes providing, by the relay, access to the second blockchain instance to the first blockchain instance via a second relay.
    [0101] In some embodiments, the blockchain network configuration indicated by the chain identifier of the second blockchain instance is identified by the second relay based on the same chain identifier as the second blockchain instance. In some embodiments, the second instance
    Petition 870190056735, of 6/19/2019, p. 44/62
    37/40 blockchain is accessed by the second relay based on the blockchain network configuration indicated by the chain identifier of the second blockchain instance. In other words, the first blockchain instance can use the same domain name as the second blockchain instance, regardless of which relay is or how many relays are used to interact with the second blockchain instance.
    [0102] In some embodiments, the blockchain network configuration indicated by the chain identifier of the second blockchain instance is identified by the second relay, according to the query information stored locally in the second relay based on the same chain identifier of the second blockchain instance .
    [0103] In some embodiments, the blockchain network configuration indicated by the chain identifier of the second blockchain instance is identified by the second relay based on the blockchain domain name of the second blockchain instance from a unified remote blockchain domain name server.
    [0104] The described features can be implemented in digital electronic circuits, or in computer hardware, firmware, software or in combinations thereof. The device can be implemented in a computer program product tangibly incorporated in an information carrier (for example, in a machine-readable storage device) for the execution of a programmable processor; and the steps of the method can be performed through a programmable processor executing an instruction program to perform the functions of the described achievements operating on the input data and generating the output. The described features can be advantageously implemented in one or more computer programs that are executable in a programmable system including, at least, a programmable processor coupled to receive the data.
    Petition 870190056735, of 6/19/2019, p. 45/62
    38/40 data and instructions therefrom, and to transmit the data and instructions to, a data storage system, at least one input device and at least one output device. A computer program is a set of instructions that can be used, directly or indirectly, on a computer to perform a certain activity or bring about a specific result. A computer program can be written in any form of programming language, including compiled or interpreted languages, and can be broken down in any form, including the way as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.
    [0105] Processors suitable for executing an instruction program include, for example, microprocessors for general and special use, and the single processor or one of multiple processors of any type of computer. In general, a processor will receive instructions and data from a read-only memory or a random access memory or both. The elements of a computer can include a processor to execute instructions and one or more memories to store instructions and data. In general, a computer can also include, or be operationally coupled to communicate with, one or more mass storage devices to store data files; such devices include magnetic disks, such as internal hard drives and removable disks; magneto-optical discs; and optical discs. Storage devices suitable for tangibly incorporating computer program instructions and data include all forms of non-volatile memory, including, for example, semiconductor memory devices, such as EPROM, EEPROM and flash memory devices; magnetic disks, such as internal hard drives and disks
    Petition 870190056735, of 6/19/2019, p. 46/62
    39/40 removable; magneto-optical discs; and CD-ROM and DVD-ROM discs. The processor and memory can be complemented, or incorporated into application-specific integrated circuits (ASICs).
    [0106] To provide interaction with a user, the features can be implemented on a computer that has a screen device such as a cathode ray tube (CRT) or liquid crystal screen (LCD) for displaying information to the user. user and a keyboard and a pointing device, such as a mouse or a trackball, by which the user can provide input to the computer.
    [0107] Features can be implemented on a computer system that includes a back-end component, such as a data server, or that includes a middleware component, such as an application server or an Internet server, or which includes a front-end component, such as a client computer that has a graphical user interface or an Internet browser, or any combination of them. The system components can be connected by any form or means of digital data communication, such as a communication network. Examples of communication networks, for example, include a local area network (LAN), a wide area network (WAN), and the computers and networks that make up the Internet.
    [0108] The computer system can include clients and servers. A client and a server, in general, are remote with each other and, in general, interact through a network, such as the one described. The client and server relationship arises because of computer programs running on the respective computers and which have a client-server relationship between them.
    [0109] In addition, the logical flows illustrated in the Figures do not require the special order shown, or sequential order, to achieve the desired results. In addition, other steps can be provided, or
    Petition 870190056735, of 6/19/2019, p. 47/62
    40/40 steps can be eliminated, from the described flows, and other components can be added or removed from the described systems. Therefore, other realizations are within the scope of the following claims.
    [0110] A number of embodiments of the present invention have been described. However, it will be understood that various modifications can be made without departing from the scope of the present invention. Therefore, other realizations are within the scope of the following claims.
    权利要求:
    Claims (12)
    [1]
    Claims
    1. COMPUTER IMPLEMENTED METHOD FOR AUTHENTICATING A UNIFIED BLOCKCASE DOMAIN NAME (UBCDN) of a blockchain instance, the method characterized by the fact that it comprises the steps of:
    - obtaining, via a computer system (106,108), a unified blockchain domain name (UBCDN) message from a blockchain instance, in which the UBCDN message comprises:
    - a blockchain instance UBCDN comprising:
    - a blockchain domain name of the blockchain instance, where the blockchain domain name is a unique identifier of the blockchain instance in a unified blockchain network comprising a series of blockchain instances that are communicatively linked by two or more relays and where the name blockchain domain name comprises a readable tag and
    - a blockchain instance chain identifier uniquely corresponding to the blockchain domain name ·,
    - a digital signature of a UBCDN owner of the blockchain instance (a UBCDN owner) in UBCDN; and
    - a UBCDN domain certificate;
    - checking whether the UBCDN domain certificate is issued by a trusted certification authority (CA) using a public CA key; and
    - checking whether the UBCDN is issued by the UBCDN owner using a public key from the UBCDN owner.
    [2]
    2. METHOD, according to claim 1, characterized by the fact that the computing system (106,108) serves as a third of the unified blockchain network.
    [3]
    3. METHOD, according to claim 1, characterized
    Petition 870190056735, of 6/19/2019, p. 49/62
    2/5 by the fact that the computing system (106, 108) serves as a client node of a second blockchain instance different from the blockchain instance in the unified blockchain network, and the method further comprises:
    - in response to verification that the UBCDN is issued by the UBCDN owner; and checking whether the UBCDN of UBCDN is issued by a trusted CA, conducting cross-chain transactions between the blockchain instance and the second blockchain instance based on the blockchain domain name of the blockchain instance.
    [4]
    4. METHOD, according to claim 1, characterized by the fact that the UBCDN domain certificate comprises:
    - the blockchain domain name of the blockchain instance ·,
    - the public key of the UBCDN owner; and
    - a digital CA signature on the blockchain domain name of the blockchain instance and the public key of the UBCDN owner.
    [5]
    5. METHOD, according to claim 4, characterized by the fact that the digital signature of the CA is obtained by signing the CA on the blockchain domain name of the blockchain instance and the public key of the UBCDN owner using a private key from the corresponding CA the CA public key; and
    - where verification that the UBCDN domain certificate is issued by a trusted CA using a CA public key comprises verification that the UBCDN domain certificate is issued by the CA using the domain certificate, the CA digital signature, and CA public key.
    [6]
    6. METHOD, according to claim 4, characterized by the fact that the digital signature of the UBCDN owner is obtained by the UBCDN owner by signing the UBCDN using a private key corresponding to the public key of the UBCDN owner; and
    - where checking whether the UBCDN of the blockchain instance is
    Petition 870190056735, of 6/19/2019, p. 50/62
    3/5 issued by the UBCDN owner using a public key from the UBCDN owner comprises checking whether the UBCDN is issued by the UBCDN owner using UBCDN, the digital signature of the UBCDN owner UBCDN and the public key of the UBCDN owner.
    [7]
    7. METHOD implemented by the computer of an owner of a unified blockchain domain name (UBCDN) of a blockchain instance, characterized by the fact that it comprises:
    - obtaining, by a UBCDN owner of a blockchain instance (a UBCDN owner) from a trusted certification authority (CA), a blockchain instance UBCDN domain certificate, in which a blockchain instance UBCDN comprises :
    - a blockchain domain name of the blockchain instance, where the blockchain domain name is a unique identifier of the blockchain instance in a unified blockchain network comprising a series of blockchain instances that are communicatively linked by two or more relays and where the name blockchain domain name comprises a readable tag and
    - a blockchain instance chain identifier uniquely corresponding to the blockchain domain name, where the chain identifier indicates a blockchain network configuration of the blockchain instance ·,
    - where the UBCDN domain certificate comprises:
    - the blockchain domain name of the blockchain instance ·,
    - a public key of the UBCDN owner; and
    - a digital CA signature on the blockchain domain name of the blockchain instance and the public key of the UBCDN owner;
    - the signature, by the UBCDN owner, of the UBCDN of the blockchain instance ·, and
    - the publication, by the UBCDN owner, of a message from
    Petition 870190056735, of 6/19/2019, p. 51/62
    4/5
    Blockchain instance UBCDN, where the UBCDN message comprises:
    - the UBCDN of the blockchain instance ·,
    - a digital signature of the UBCDN owner resulting from the UBCDN signature; and
    - the UBCDN domain certificate.
    [8]
    8. METHOD, according to claim 7, characterized by the fact that it still comprises:
    - the identification of an updated chain identifier of the blockchain instance indicating an updated blockchain network configuration of the blockchain instance ·,
    - the signature, by the UBCDN owner, of an updated UBCDN of the blockchain instance comprising the blockchain domain name of the blockchain instance and the updated chain identifier of the blockchain instance ·, and
    - the publication, by the UBCDN owner, of an updated UBCDN message from the blockchain instance, in which the updated UBCDN message includes:
    - the updated UBCDN of the blockchain instance ·,
    - an updated digital signature of the UBCDN owner resulting from the updated UBCDN signature; and
    - the UBCDN domain certificate.
    [9]
    9. COMPUTER PROGRAM PRODUCT, characterized by a computer coupled to one or more processors and which has instructions stored on it that, when executed by one or more processors, cause one or more processors to perform operations according to the method of a or more processors, as defined in any of claims 1 to 6.
    [10]
    10. SYSTEM FOR IMPLEMENTING A METHOD,
    Petition 870190056735, of 6/19/2019, p. 52/62
    5/5 that includes:
    - a computing device (106, 108); and
    - a human-readable storage device characterized by a computer coupled to the computing device (106, 108) and which has instructions stored on it which, when executed by the computing device (106, 108), cause the computing device (106, 108 ) perform the operations according to the method as defined in any of claims 1 to 6.
    [11]
    11. COMPUTER PROGRAM PRODUCT, characterized by a computer, coupled to one or more processors and which has instructions stored on it that, when executed by one or more processors, cause one or more processors to perform operations according to the method of one or more processors, as defined in any one of claims 7 to 8.
    [12]
    12. SYSTEM FOR IMPLEMENTING A METHOD, which includes:
    - a computing device (106, 108); and
    - a human-readable storage device characterized by a computer coupled to the computing device (106, 108) and which has instructions stored on it which, when executed by the computing device (106, 108), cause the computing device (106, 108 ) perform the operations according to the method as defined in any of claims 7 to 8.
    类似技术:
    公开号 | 公开日 | 专利标题
    BR112019008000A2|2019-09-10|computer-implemented method for authenticating a domain name, storage medium, and system
    BR112019007991A2|2019-09-10|computer-implemented method of a relay for cross-chain interactions in a unified trusted protocol network, computer readable, non-transient storage media, and system
    BR112019008025A2|2019-09-10|computer-implemented method, non-transient computer-readable storage medium, and system
    同族专利:
    公开号 | 公开日
    US20210176074A1|2021-06-10|
    ZA201902483B|2021-05-26|
    CA3041203A1|2019-04-18|
    KR102160369B1|2020-09-28|
    JP6821020B2|2021-01-27|
    EP3549324A4|2020-01-15|
    AU2018347192A1|2020-06-04|
    PL3549324T3|2021-07-19|
    US20190253259A1|2019-08-15|
    CA3041203C|2021-01-19|
    EP3549324B1|2020-10-07|
    PH12019500871A1|2019-12-02|
    WO2019072272A3|2019-09-12|
    US20200186364A1|2020-06-11|
    CN111434085A|2020-07-17|
    EP3549324A2|2019-10-09|
    MX2019004660A|2019-08-12|
    US11102011B2|2021-08-24|
    AU2018347192B2|2020-06-25|
    US10931462B2|2021-02-23|
    KR20200059184A|2020-05-28|
    US10680828B2|2020-06-09|
    JP2020511010A|2020-04-09|
    ES2842976T3|2021-07-15|
    RU2718959C1|2020-04-15|
    SG11201903478WA|2019-05-30|
    WO2019072272A2|2019-04-18|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    US7418504B2|1998-10-30|2008-08-26|Virnetx, Inc.|Agile network protocol for secure communications using secure domain names|
    US6502135B1|1998-10-30|2002-12-31|Science Applications International Corporation|Agile network protocol for secure communications with assured system availability|
    US7200144B2|2001-10-18|2007-04-03|Qlogic, Corp.|Router and methods using network addresses for virtualization|
    US7953074B2|2003-01-21|2011-05-31|Emulex Design And Manufacturing Corporation|Apparatus and method for port polarity initialization in a shared I/O device|
    KR101029364B1|2008-06-24|2011-04-13|주식회사 케이티|Mobile terminal unit for providing integrated web browsing service, mobile communication system, local area wireless communication system and method thereof|
    US7940740B2|2009-02-03|2011-05-10|Motorola Mobility, Inc.|Apparatus and method for communicating and processing a positioning reference signal based on identifier associated with a base station|
    US8730925B2|2009-04-09|2014-05-20|Motorola Mobility Llc|Method and apparatus for generating reference signals for accurate time-difference of arrival estimation|
    WO2012050841A1|2010-09-28|2012-04-19|Research In Motion Corporation|Method and apparatus for releasing connection with local gw when ue moves out of the residential/enterprise network coverage|
    US8706739B1|2012-04-26|2014-04-22|Narus, Inc.|Joining user profiles across online social networks|
    MY175274A|2012-10-29|2020-06-17|Ericsson Telefon Ab L M|Protecting a payload sent in a communications network|
    TWI523471B|2014-03-27|2016-02-21|國立臺北科技大學|Method of transmitting by relay server for advanced domain name system|
    WO2015170862A1|2014-05-05|2015-11-12|엘지전자 주식회사|Method for establishing plurality of pdn connections by means of csipto|
    US10396992B2|2014-06-30|2019-08-27|Vescel, Llc|Authentication of a user and/or a device through parallel synchronous update of immutable hash histories|
    US10375514B2|2014-07-29|2019-08-06|GeoFrenzy, Inc.|Systems, methods and apparatus for geofence networks|
    US10230526B2|2014-12-31|2019-03-12|William Manning|Out-of-band validation of domain name system records|
    WO2017122187A2|2016-01-15|2017-07-20|Enrico Maim|Methods and systems implemented in a network architecture with nodes capable of performing message-based transactions|
    US10484168B2|2015-03-02|2019-11-19|Dell Products L.P.|Methods and systems for obfuscating data and computations defined in a secure distributed transaction ledger|
    JP2018516026A|2015-03-20|2018-06-14|リヴェッツ・コーポレーションＲｉｖｅｔｚ Ｃｏｒｐ．|Automatic device integrity authentication using blockchain|
    US10963881B2|2015-05-21|2021-03-30|Mastercard International Incorporated|Method and system for fraud control of blockchain-based transactions|
    US9870562B2|2015-05-21|2018-01-16|Mastercard International Incorporated|Method and system for integration of market exchange and issuer processing for blockchain-based transactions|
    US10084794B2|2015-06-02|2018-09-25|ALTR Solutions, Inc.|Centralized access management of web-based or native applications|
    US10346826B2|2015-07-28|2019-07-09|Wesley John Boudville|Blockchain and deep links for mobile apps|
    US10303887B2|2015-09-14|2019-05-28|T0.Com, Inc.|Data verification methods and systems using a hash tree, such as a time-centric merkle hash tree|
    EP3193299A1|2016-01-15|2017-07-19|Accenture Global Services Limited|Device, method and system for autonomous selection of a commodity supplier through a blockchain distributed database|
    US20170236123A1|2016-02-16|2017-08-17|Blockstack Inc.|Decentralized processing of global naming systems|
    EP3420514A1|2016-02-23|2019-01-02|Nchain Holdings Limited|A method and system for securing computer software using a distributed hash table and a blockchain|
    WO2017145049A1|2016-02-23|2017-08-31|nChain Holdings Limited|Consolidated blockchain-based data transfer control method and system|
    WO2017164784A1|2016-03-24|2017-09-28|Telefonaktiebolaget Lm Ericsson |Data object transfer between network domains|
    US9855785B1|2016-04-04|2018-01-02|Uipco, Llc|Digitally encoded seal for document verification|
    US20170302663A1|2016-04-14|2017-10-19|Cisco Technology, Inc.|BLOCK CHAIN BASED IoT DEVICE IDENTITY VERIFICATION AND ANOMALY DETECTION|
    US11223598B2|2016-05-03|2022-01-11|Nokia Of America Corporation|Internet security|
    JP6628188B2|2016-05-10|2020-01-08|日本電信電話株式会社|Payment system, payment method, transaction generation device, and transaction generation program|
    WO2017218983A1|2016-06-16|2017-12-21|The Bank Of New York Mellon|Distributed, centrally authored block chain network|
    EP3476102B1|2016-06-24|2020-06-17|Innogy Innovation Gmbh|Augmented reality system|
    WO2018006945A1|2016-07-05|2018-01-11|Rwe International Se|Observation system|
    CN106210171A|2016-07-25|2016-12-07|宁圣金融信息服务（上海）有限公司|A kind of block chain domain name analysis system|
    US10860735B2|2016-08-05|2020-12-08|Sensoriant, Inc.|Database system for protecting and securing stored data using a privacy switch|
    US10361869B2|2016-08-23|2019-07-23|International Business Machines Corporation|Event ledger|
    US10339014B2|2016-09-28|2019-07-02|Mcafee, Llc|Query optimized distributed ledger system|
    US11258587B2|2016-10-20|2022-02-22|Sony Corporation|Blockchain-based digital rights management|
    US11182851B2|2016-10-20|2021-11-23|International Business Machines Corporation|Inter-ledger messaging in a blockchain|
    CN106991334B|2016-11-24|2021-03-02|创新先进技术有限公司|Data access method, system and device|
    WO2018103850A1|2016-12-08|2018-06-14|Telefonaktiebolaget Lm Ericsson |Method and apparatus for creating a finite blockchain|
    US20200250694A1|2016-12-12|2020-08-06|Dosh Holdings, Inc.|Matching offers transactions across heterogeneous, multi-entity distributed computing platforms and settlement|
    US10686590B2|2016-12-23|2020-06-16|Joseph Santilli|Methods and systems for crowdsourcing an outcome to an issue|
    US10164983B2|2017-01-20|2018-12-25|Verizon Patent And Licensing Inc.|Distributed authentication for internet-of-things resources|
    RU2639015C1|2017-01-26|2017-12-19|Игорь Сан-Сенович Дю|Authenticity and quality control procedure of production in the process of manufacture and implementation|
    US9992022B1|2017-02-06|2018-06-05|Northern Trust Corporation|Systems and methods for digital identity management and permission controls within distributed network nodes|
    JP6341491B1|2017-02-21|2018-06-13|株式会社三菱Ｕｆｊ銀行|Signal processing method and signal processing program|
    US11196573B2|2017-03-06|2021-12-07|Nokia Technologies Oy|Secure de-centralized domain name system|
    AU2018230763A1|2017-03-08|2019-10-31|Ip Oversight Corporation|System and method for creating commodity asset-secured tokens from reserves|
    CN107196900B|2017-03-24|2020-04-24|创新先进技术有限公司|Consensus checking method and device|
    US10848322B2|2017-03-24|2020-11-24|Cable Television Laboratories, Inc|System and method for distributed PKI root|
    JP6904002B2|2017-03-30|2021-07-14|ソニーグループ株式会社|Information processing device and information processing method|
    WO2018176406A1|2017-03-31|2018-10-04|北京大学深圳研究生院|Top-level domain name management method and system based on alliance chain|
    US11095432B2|2017-04-05|2021-08-17|Samsung Sds Co., Ltd.|System for processing data based on blockchain and operating method thereof|
    US10102265B1|2017-04-12|2018-10-16|Vijay K. Madisetti|Method and system for tuning blockchain scalability for fast and low-cost payment and transaction processing|
    US10412045B1|2017-04-17|2019-09-10|Verisign, Inc.|Domain name registration reservation through the use of encoding domain names for pools|
    US20190166085A1|2017-04-19|2019-05-30|Peking University Shenzhen Graduate School|Blockchain-based domain name resolution system|
    US10320574B2|2017-05-05|2019-06-11|International Business Machines Corporation|Blockchain for open scientific research|
    US20180330386A1|2017-05-09|2018-11-15|Heonsu Kim|Proof of ownership device and methods for using the same|
    CN107231299A|2017-06-07|2017-10-03|众安信息技术服务有限公司|A kind of chain route and realized the system that block chain communicates across chain|
    US20190012660A1|2017-07-06|2019-01-10|Robert Masters|Systems and methods for providing an architecture for an internet-based marketplace|
    US10984134B2|2017-07-14|2021-04-20|Microsoft Technology Licensing, Llc|Blockchain system for leveraging member nodes to achieve consensus|
    CN107566337B|2017-07-26|2019-08-09|阿里巴巴集团控股有限公司|Communication means and device between a kind of block chain node|
    CN107592292B|2017-07-26|2019-08-09|阿里巴巴集团控股有限公司|A kind of block chain communication method between nodes and device|
    US11146380B2|2017-08-03|2021-10-12|Parity Technologies Ltd.|Methods and systems for a heterogeneous multi-chain framework|
    US20190066068A1|2017-08-22|2019-02-28|Sap Se|Transaction Platform Providing Unified Interaction with Multiple Heterogeneous Blockchains|
    US20190073670A1|2017-09-05|2019-03-07|PeerNova, Inc.|Capturing Related Events in Cryptographically Linked Records|
    US10938567B2|2017-09-12|2021-03-02|Kadena Llc|Parallel-chain architecture for blockchain systems|
    WO2019056006A1|2017-09-18|2019-03-21|James Leftwich|Method for producing a dynamically ordered queue|
    CN107613041B|2017-09-22|2020-06-05|中国互联网络信息中心|Domain name management system, domain name management method and domain name resolution method based on block chain|
    US10958418B2|2017-10-10|2021-03-23|Chromata Corporation|System and method for a blockchain network with heterogeneous privacy|
    US20190116038A1|2017-10-12|2019-04-18|Rivetz Corp.|Attestation With Embedded Encryption Keys|
    US11121870B2|2017-10-12|2021-09-14|Mastercard International Incorporated|Method and system for interacting public and private blockchains with controlled participation|
    CN107888562B|2017-10-13|2019-12-27|布比（北京）网络技术有限公司|Data verification and transceiving method, node and system for parallel link access to interconnection chain|
    WO2019109003A1|2017-11-30|2019-06-06|Visa International Service Association|Blockchain system for confidential and anonymous smart contracts|
    US10657261B2|2017-11-30|2020-05-19|Mocana Corporation|System and method for recording device lifecycle transactions as versioned blocks in a blockchain network using a transaction connector and broker service|
    KR20190067581A|2017-12-07|2019-06-17|한국전자통신연구원|Apparatus and method for distributed processing of blockchain transactions|
    US11176101B2|2018-02-05|2021-11-16|Bank Of America Corporation|System and method for decentralized regulation and hierarchical control of blockchain architecture|
    CN108347486A|2018-02-12|2018-07-31|众安信息技术服务有限公司|Across chain communication means, device and system based on block chain|
    US20190251199A1|2018-02-14|2019-08-15|Ivan Klianev|Transactions Across Blockchain Networks|
    CN108415784B|2018-02-27|2020-04-24|阿里巴巴集团控股有限公司|Cross-block-chain interaction method, device, system and electronic equipment|
    CN108712257B|2018-04-03|2020-04-17|阿里巴巴集团控股有限公司|Cross-block-chain authentication method and device and electronic equipment|
    CN108683630B|2018-04-03|2020-05-29|阿里巴巴集团控股有限公司|Cross-block-chain authentication method and device and electronic equipment|
    JP2019185296A|2018-04-06|2019-10-24|富士通株式会社|Data managing device, data managing program and data managing method|
    US11132707B2|2018-04-25|2021-09-28|At&T Intellectual Property I, L.P.|Blockchain solution for an automated advertising marketplace|
    CN108665365B|2018-05-16|2021-07-13|四川大学|Mixed block chain architecture system, processing method and processing system|
    CN108712506B|2018-05-31|2021-02-02|中国联合网络通信集团有限公司|Block chain node communication method and device and block chain node|
    US11196551B2|2018-06-27|2021-12-07|International Business Machines Corporation|Automated task management on a blockchain based on predictive and analytical analysis|
    US20200034833A1|2018-07-24|2020-01-30|Go Daddy Operating Company, LLC|System for deterministic processing of temporally significant, sequentially significant and/or cost conscious digital ledger publications|
    CN109145205B|2018-07-27|2020-09-01|阿里巴巴集团控股有限公司|Cross-chain data operation method and device based on block chain|
    US20200042989A1|2018-07-31|2020-02-06|Ramesh Ramadoss|Asset-backed tokens|
    US20200050690A1|2018-08-07|2020-02-13|International Business Machines Corporation|Preservation of uniqueness and integrity of a digital asset|
    US11176571B2|2018-09-06|2021-11-16|MadHive, Inc.|Methods and system for serving targeted advertisements to a consumer device|
    US11204751B2|2018-09-07|2021-12-21|International Business Machines Corporation|Mitigating incompatibilities due to code updates in a system containing multiple networked electronic control units|
    US10404467B1|2018-09-09|2019-09-03|Tyson York Winarski|Blockchain digest augmention of media files including group-of-pictures video streams for MXF files|
    US20190050854A1|2018-09-28|2019-02-14|Intel Corporation|Blockchain-based digital data exchange|
    US20200118068A1|2018-10-10|2020-04-16|QuestaWeb, Inc.|Hierarchical Blockchain Architecture for Global Trade Management|
    US11093479B2|2018-11-06|2021-08-17|Workday, Inc.|Ledger data generation and storage for trusted recall of professional profiles|
    AU2018348320B2|2018-11-16|2020-01-16|Advanced New Technologies Co., Ltd.|A domain name scheme for cross-chain interactions in blockchain systems|
    CA3041208C|2018-11-16|2021-05-04|Alibaba Group Holding Limited|Cross-chain interactions using a domain name scheme in blockchain systems|
    AU2018347192B2|2018-11-16|2020-06-25|Advanced New Technologies Co., Ltd.|A domain name management scheme for cross-chain interactions in blockchain systems|
    CN110311790B|2019-06-28|2020-07-28|阿里巴巴集团控股有限公司|Method and device for sending authenticable message in cross-link mode|AU2018347192B2|2018-11-16|2020-06-25|Advanced New Technologies Co., Ltd.|A domain name management scheme for cross-chain interactions in blockchain systems|
    CA3041208C|2018-11-16|2021-05-04|Alibaba Group Holding Limited|Cross-chain interactions using a domain name scheme in blockchain systems|
    CN111899104A|2018-11-27|2020-11-06|创新先进技术有限公司|Service execution method and device|
    CN110046901B|2018-12-28|2020-06-30|阿里巴巴集团控股有限公司|Credibility verification method, system, device and equipment of alliance chain|
    US10790990B2|2019-06-26|2020-09-29|Alibaba Group Holding Limited|Ring signature-based anonymous transaction|
    CN110417742B|2019-06-28|2020-11-06|创新先进技术有限公司|Method, device and storage medium for cross-link sending, transferring and receiving authenticable message|
    CN110430235B|2019-06-28|2020-11-03|创新先进技术有限公司|Method, apparatus, storage medium and computing device for cross-chain transmission of authenticatable messages|
    US10742415B2|2019-06-28|2020-08-11|Alibaba Group Holding Limited|Method and apparatus for inter-blockchain transmission of authenticable message|
    US11251966B2|2019-06-28|2022-02-15|Advanced New Technologies Co., Ltd.|Sending cross-chain authenticatable messages|
    US11196771B2|2019-07-16|2021-12-07|International Business Machines Corporation|Multi-domain blockchain network with data flow control|
    SG10201907333RA|2019-08-08|2020-01-30|Alibaba Group Holding Ltd|Methods And Devices For Executing Cross-Chain Anonymous Multi-Swap Contracts|
    CN112468525A|2019-09-06|2021-03-09|傲为信息技术有限公司|Domain name management system based on block chain|
    KR102320550B1|2019-12-05|2021-11-02|주식회사 더블체인|Did-based interchain system and method for data exchange/transaction thereof|
    CN112583596B|2020-06-08|2021-09-28|四川大学|Complete cross-domain identity authentication method based on block chain technology|
    CN112380294B|2020-12-31|2021-04-06|支付宝信息技术有限公司|Block chain cross-chain access method and device|
    CN112737793B|2021-03-30|2021-09-28|支付宝信息技术有限公司|Method and device for updating block chain domain name configuration|
    CN113850599B|2021-12-01|2022-02-15|南京金宁汇科技有限公司|Cross-link transaction method and system applied to alliance link|
    法律状态:
    2021-04-20| B25A| Requested transfer of rights approved|Owner name: ADVANTAGEOUS NEW TECHNOLOGIES CO., LTD. (KY) |
    2021-05-11| B25A| Requested transfer of rights approved|Owner name: ADVANCED NEW TECHNOLOGIES CO., LTD. (KY) |
    2021-10-05| B350| Update of information on the portal [chapter 15.35 patent gazette]|
    2021-12-28| B09A| Decision: intention to grant [chapter 9.1 patent gazette]|
    优先权:
    申请号 | 申请日 | 专利标题
    PCT/CN2018/115921|WO2019072272A2|2018-11-16|2018-11-16|A domain name management scheme for cross-chain interactions in blockchain systems|
    [返回顶部]